feat: implement toggle for redacting PII in ManualVerification during user retirement#38890
Merged
Merged
Conversation
ktyagiapphelix2u
force-pushed
the
ktyagi/BOMS-680
branch
from
July 15, 2026 08:41
9b596a2 to
24c022f
Compare
ktyagiapphelix2u
force-pushed
the
ktyagi/BOMS-680
branch
from
July 15, 2026 08:43
24c022f to
2293f73
Compare
ttak-apphelix
approved these changes
Jul 15, 2026
bmtcril
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an optional way to remove old ManualVerification personal data during LMS retirement. By default, nothing changes and the records are kept. If
REDACT_MANUAL_VERIFICATION_HISTORICAL_PIIis turned on, the system first removes personal information (like the name) from ManualVerification records and then deletes those records. Tests confirm that the data is removed before deletion and that only the correct records are affected.Private Jira Ticket
https://2u-internal.atlassian.net/browse/BOMS-680